Skip to content

Conversation

@IsaacMilarky
Copy link
Collaborator

Add Edits From NPD Repo

Problem

Currently, we have issues with our contributors.yml workflow. We also do not have a default .gitleaks.toml file template that we include in the repositories that are generated.

Solution

In the contributors.yml file, use a personal access token in the checkout action to make sure that we are using a user that has push access to main. This way we can circumvent branch protections for the action.

Also, added a .gitleaks.toml file to all tiers as well as this repository. This file includes gitleaks regex patterns for common keys. It can and should be configured for different project types.

Copy link
Contributor

@sachin-panayil sachin-panayil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Collaborator

@natalialuzuriaga natalialuzuriaga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After resolving the secrets variable error, this should be good to go!

Another question: does the .gitleaks.toml file have to live in the root directory? Could this be moved to the .github directory?

@natalialuzuriaga natalialuzuriaga changed the base branch from main to dev September 23, 2025 20:47
Copy link
Contributor

@decause-gov decause-gov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM +1 🚢

This blocking on anything else?

@IsaacMilarky
Copy link
Collaborator Author

After resolving the secrets variable error, this should be good to go!

Another question: does the .gitleaks.toml file have to live in the root directory? Could this be moved to the .github directory?

Sounds good! I have updated the raw tag problem finally. As for the .gitleaks.toml question, we could move it into the .github directory however we would have to configure gitleaks to look for the file in that location explicitly.

I have amended the gitleaks workflow to look for the config in that location and moved the files accordingly.

Copy link
Collaborator

@natalialuzuriaga natalialuzuriaga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and all is working!! LGTM 🙌

@natalialuzuriaga
Copy link
Collaborator

After resolving the secrets variable error, this should be good to go!
Another question: does the .gitleaks.toml file have to live in the root directory? Could this be moved to the .github directory?

Sounds good! I have updated the raw tag problem finally. As for the .gitleaks.toml question, we could move it into the .github directory however we would have to configure gitleaks to look for the file in that location explicitly.

I have amended the gitleaks workflow to look for the config in that location and moved the files accordingly.

Super clutch, thank you!

@natalialuzuriaga natalialuzuriaga merged commit def63c3 into dev Oct 23, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants